USoft 11
September 2025
The release notes are an addition to the product information in the Knowledge Base.
The Knowledge Base describes the most recently released version of the software. By contrast, the Release Notes in this document describe changes by individual patch release.
This page contains the following sections:
- Introduction to USoft 11.0.
- New Functionality and Enhancements in in USoft 11.0.
- Removed and deprecated functionality in USoft 11.0.
Introduction
USoft Product Documentation
For general product documentation, please go to the Knowledge Base at docs.usoft.com.
Context Help
USoft Definer and USoft Authorizer have "What's This?" context help on individual fields. To get help on a field in a specific window, click the "What's This?" icon (the question mark) on the ribbon bar, then click in the field.
USoft Windows Designer and USoft Web Designer have context help for individual properties of controls. To get help on a property of an object, open the Property Inspector for the object, and click on the property name. The help text appears in the lower area of the Property Inspector. You may have to toggle the '?' button to get it displayed.
USoft Studio has extensive in-product help of its own. Click the Help menu, or use the Help tile in the Home page, or click '?' icons for help on individual pages.
USoft Support
For all communication related to this release, please use our Customer Portal.
Your feedback helps us improve!
License
Before you can install or use USoft Developer Series products on your system, you must have a valid LICENSE.DAT file. During the setup procedure, you will be asked to provide the location of this LICENSE.DAT file. Find details in the "USoft for administrators" section on docs.usoft.com.
Getting Started
Follow these general steps to get started with USoft. Please find details of these steps in the "USoft for administrators" section on docs.usoft.com.
- Make sure that your system and RDBMS satisfy USoft system requirements.
- Install the USoft software. For details of the following steps , search "USoft Binder" on docs .usoft.com.
- Set up a new project using USoft Binder.
- Start the USoft product from the work area of the USoft Binder.
New Functionality and Enhancements in USoft 11.0
This section provides you with an overview of the most important new functionality and enhancements in the product. Many of these enhancements are the result of customer requests and feedback.
Version control
The USoft Developer platform now supports version control.
Instead of working on a central database, it is now also possible for members of a USoft team to work on a local , de-centralized database and then push work to a central file-based version control system like GIT or SubVersio n. USoft Definer, USoft Windows Designer, USoft Web Designer, USoft Service Definer, USoft Delivery Manager and USoft Benchmark now all support version control.
Updated runtime web UIs
The runtime web UIs output by USoft Web Designer now have a cleaner HTML5 structure. All JavaScript output by USoft has moved to modules. This ensures a clean separation when 3rd-party libraries are combined with USoft web solutions. Interference between 3rd -party functions and similar USoft embedded functions is prevented.
Revised web UI API
USoft Web Designer exposes an API of UDB objects that allows a web UI to communicate with the Rules Engine. This code layer has been brought in line with current JavaScript standards. Obsolete technologies (jQuery, jQuery UI, handlebars, older Bootstrap versions) are being phased out and replaced by modern standards (latest Bootstrap, Vue3). This enables reactive pages among other things.
In USoft 11, the entire API has been rewritten and its coding restyled to using modules and classes. The resulting API is easier to maintain and works more like modern libraries, so that past design issues can be addressed upfront instead of being ‘patched away’.
General remarks
Most outputs of API functions have changed considerably, but the way the functions are called is mostly unchanged.
Promises are used throughout; callback functions are deprecated. Callback functions are still available , albeit with a deprecation message when encountered.
Synchronous calls using the ‘async: false’ option have been dropped. If you need the next statement to be executed when the current statement is finished, use proper Promise behavior using the await keyword, or use proper chaining functions. Correspondingly, ‘promise’ options of function s have been dropped. Instead, every function that had a promise option or callback functions now automatically returns an instance of UdbPromise. UdbPromise replac es the earlier udbPromise class.
- ‘success’ and ‘error’ callback function options are deprecated.
- ‘async’ function option has been dropped.
Maximum use is made of classes. Outputs of API functions are now always instances of these classes, instead of some generic JSON object. For example, the $.udb() function now returns an array of objects instead of strings. Functions called on these arrays, however, still work the same way as before.
Reference objects (context, query details) in arrays (e.g. of data sources, rows, etc) contain actual objects instead of string references, e.g. frame context information now takes the form of context objects instead of their string ids.
jQuery is no longer used . Events are now handled by native constructions, and certain selectors that were specifically jQuery, and also our own ‘pseudo -selectors’ , can no longer be used. Convenient UI functions that were commonly used , eg., .addClass() , .removeClass(), .data(), .on(), .off() , .trigger() , have been added to the native classes of the HTML DOM objects themselves now.
If you still require jQuery, you can simply add it to the application.html file. Be aware that USoft default controls will not use jQuery calls.
$.udb() Functions and Changes
| Function | Change / Notes |
|---|---|
.acceptLookupValue() | Option keepOpen dropped (lookup display via DialogControls no longer available). |
.applyCurrentContext() | New parameter: newPageAlias. |
.context() | Parameter create dropped. |
.data.format | Moved to .ioFormat. |
.executeSQLStatement() | Deprecated; use SQLDataSources instead. |
.groupRequests() | Obsolete and no longer functional. |
.off(), .on(), .trigger() | No longer use jQuery to register/handle events. |
.setTimeout() | Use $.udb.setTimeout('current') instead of $.udb.setTimeout.current. |
.startPage() | No longer part of public API. |
.status.loggedIn() | Now supports optional parameter fn. |
.status.setLoginStatus() | Moved to .setLoginStatus(). |
$.udb.ui Functions
| Function | Change / Notes |
|---|---|
$.udb.dialog | benchmark option dropped. dialogClass option added (default null). icon default changed to bi-exclamation-triangle-fill. Now always returns a UdbPromise. |
$.udb.input | benchmark option dropped.dialogClass option added (default null). Now always returns a UdbPromise. |
$.udb.wait | Now always returns a UdbPromise. New feature: call count. Multiple $.udb.wait(true) calls must be ended with the same number of $.udb.wait(false) calls. Use $.udb.wait('off') to hide immediately. |
$.udb.opacity | Now always returns a UdbPromise. |
$.udb.upload | Now always returns a UdbPromise. |
$.udb(<dsRef>) Functions
| Function | Change / Notes |
|---|---|
$.udb(<dsRef>) and $.udbMeta(<dsRef>) | Merged into $.udb(<dsRef>). Output changed to UdbDsc[] of UdbDataSource instances. |
.busy() | New function. |
.cols(), .searchCols() | Return UdbCols[] of UdbColumn instances. |
containsGetValue() | Dropped. |
.context() | New function. |
.data() | Now returns an instance of UdbDataSource (e.g., UdbTableDataSource) instead of generic JSON. |
.dataInfo() | Replaced by .meta(). |
.extraKeys() | New function. |
.hasChild() | New function. |
.hasLookups() | New function. |
.isJoined() | Deprecated (joined tables via Joined property no longer supported). |
.isOnCurrentPage() | New function. |
.isQueried() | New function. |
.joins() | Deprecated (joined tables via Joined property no longer supported). |
.keyCols() | Renamed to .keys(). |
.mainDataSource() | New function. |
.meta() | Same array, replaces $.udbMeta(<dsRef>). |
.realDataSource() | Now returns the actual object, not its ID. |
.setBusy() | New function. |
$.udb(<dsRef>).rowSet(<rowSetRef>) Functions
| Function | Change / Notes |
|---|---|
| (general) | Output changed to UdbRowSets[] of UdbRowSet instances. |
.context() | New function. |
.data() | Dropped. |
.rows() | Returns UdbRows[] of UdbRecord instances. |
$.udb(<dsRef>).rowSet(<rowSetRef>).rows(<ref1>,<ref2>) Functions
| Function | Change / Notes |
|---|---|
| (general) | Output changed to UdbRows[] of UdbRecord instances. |
.cols() | Returns UdbCols[] of UdbColumn + UdbRecord instances. |
.context() | New function. |
.data() | Dropped. |
.joinedVal() | Deprecated (joined tables via Joined property no longer supported). |
.keysString() | full parameter dropped (always returns full keys). |
.keysXML() | Obsolete, no longer supported. |
$.udb(<dsRef>).rowSet(<rowSetRef>).rows(<ref1>,<ref2>).cols(<colRef>) Functions
| Function | Change / Notes |
|---|---|
cols(), colsMeta() | Merged into one structure: UdbCols[] of UdbColumn instances. |
.context() | New function. |
.isKey() | Dropped. |
.label() | Dropped (replaced earlier by .prompt() in 10.1). |
.meta() | Dropped. |
Object extension functions
USoft 10.1 offered extra functionality added to various kind of objects, eg., .forEachValue() and .forEachKey(), .map(), but these could cause name clashes with third -party libraries. These functions (including some added as of USoft 11) have been moved to a .usoft extension. Use a ‘.usoft’ prefix to access the USoft functions on the prototypes, eg., object.usoft.map() for object.map()
Improved web UI testing suite
USoft Web Benchmark, the embedded web UI test recording, playback, and benchmarking tool, now has an improved user experience, making web testing simpler and more fun.
Template defaults for web UIs
You can now replace the USoft factory default for web pages by a custom default. You can re -use this custom default as a template in multiple applications or Development environments. This prevents low -code developers from painstakingly “painting” individual details of UI controls in web pages. “Painting” is now only needed if the web page requires special features.
SBVR colour -coded formulations in USoft Definer
USoft 11 features improved integration with USoft Studio contents. The clarity and ease -of-use of colour -coded SBVR formulations is now available in USoft Definer's development environment.
Colour -coding appears automatically, not just in the "Business Rules and other Formulations" window, but also in all the windows for implementations connected to business rules, for example Constaints, Jobs, and Components.
When you import formulations from USoft Studio to USoft Definer using the "Import from Studio"bridge that was already available in USoft 10, USoft Definer now registers where the formulationscame from. This allows it to provide automatic click -through hyperlinks from SBVR conceptscoloured in green or blue to the relevant concept page in your Studio project in the cloud.
In preparation for further developments, a USoft Definer instance can now hold multiple Studiovocabularies. However, the intended use is that you keep a 1:1 mapping between a Studioproject and a Definer instance. Use the Studio -Definer bridge for repeated synchronisationbetween the 2 tools.
In preparation for further developments, it is now also possible to edit formulations in -place inUSoft Definer and get the same automatic colour -coding as in USoft Studio. However, theintended use is that you edit and view formulations in USoft Studio and transfer them to USoftDefiner using the “Import from Studio” bridge.USoft Definer – USoft Studio alignment
The USoft Definer and USoft Studio tools have been aligned in preparation for further
integration. Desirable functionality that only existed in one of the tools has also been added to the other. Quirks that made their way into one of the tools but not the other, have beeneliminated. Terminology differences are now minimal . “Formulations” and "Vocabularies" have made theirway into USoft Definer. USoft Studio "projects" have been renamed to "vocabularies".“Classification” (both tools, with different semantics) has been renamed to “Label”.The USoft Studio – USoft Definer bridge has become more straightforward. For example, it nolonger fails if you have dropped rules in Studio that have implementations in Definer.
EAR diagrams for metadata editing
EAR diagrams in USoft 11 have been moved from USoft Studio to USoft Definer.
In USoft Definer 11, EAR diagrams have interactive behaviour. What you draw is automaticallytranslated into Definer records, and vice versa: synchronisation is 2 -way and automatic. Thiscontrasts with USoft 10, where you could only export EAR diagrams to an external file.Developers can still choose to traditionally declare their data model (their metadata) by filling ina form and then generat ing the solution. But they can now, alternatively, create metadata bydrawing E AR diagrams.
An EAR diagram is associated with a Business Object (BO). It automatically depicts the tablesassociated with that BO (whether owned by the BO or not), as well as any relationshipsconnecting these tables. In addition to EAR diagrams for B Os, an EAR diagram for the repositoryas a whole is also offered. This repository -wide diagram is useful for greenfields situations and for projects in their initial phase.
EAR diagrams will remain available in USoft Studio 4.2, but they are obsolete there. T he intendeduse is to draw EAR diagrams in USoft Definer 11. Later in the 11 series, decision models will be added to this way of working, starting with theability to draw decision tables that are automatically synchronised with metadata.
Template domains
When you create tables for USoft Definer, a small collection of default domains is now created.These are called template domains. Template domains are simple, popular data types such asShort Text, Long Text, Number, Amount, Date and Boolean. Th ey allow you to draw simple type suntil you need something more refined . You can always refine and diversify later at Domainslevel in USoft Definer, as before. Template domains enable USoft to create data model specifications from EAR diagrams, wherethere is no space for detailed domain specifications.
Browser control in C/S UIs
USoft 11 extends the versatility for traditional C/S applications for back -end power users. Anexciting new feature in this area is a new browser control that will not only display applicationdata enhanced by HTML5 but also allow instant communication with the USoft Rules Engine. Thisopens up advanced C/S data rendering and takes away the burden of developing controls usingobsolete techniques. For example, when a back -end application handles resource allocation (rooms, utilities, humanresources...) a convincing HTML5 -based representation can be displayed that behavesinteractively and updates the underlying data. Needless to say, this also facilitates hybridapplications where back -end power users experience the same look (the same datarepresentation) as end users see in web UIs.Examples of browser control implementations in USoft Definer 11 include EAR diagrams andcolour -coded USoft Studio formulations.
Support for net6
In the deployment area, the USoft 10 series already provided everything necessary for runningUSoft services in containers, both on Windows and Linux. USoft 11 continues to make this evenmore seamless. A major new advancement is that USoft 11 now uses the same long -termsupported net6 version for both Windows and Linux. The USoft 11 series will add the option toswitch to higher versions.For backwards compatibility, the Windows version still supports the Windows API, allowingexisting solutions to migrate to net6.
Security
The architecture and implementations of USoft applications are continuously adapted to theneeds that follow from PEN tests, flaws in 3rd -party libraries, and insights and requirements weget from our customer base.Passwords used by USoft applications, including RDBMS passwords, are now encrypted at alllevels and cannot be hacked from any USoft call interface:
- In USoft Binder 10, passwords were masked as *** in the command line preview s but it wasnot difficult to extract the RDBMS password. This is no longer possible because they are nowmasked in their encrypted form. This makes it easier to copy/paste a comman d line and useit in a command box.
- In Service Definer and Delivery Manager, passwords are now also stored encrypted.
- It is no longer possible to extract passwords via calls to the RulesEngine internal component.
Enhanced authorisation features
A complete overhaul of the USoft authorisation system took place in USoft 10. Role -playing wasdrawn into the development environment. This allowed much richer features than before, whenauthorisation consisted essentially in distributing RDBMS grants.USoft 11 completes this transition by adding useful extras:
- Single sign -on (SSO) in C/S
- Simplified user model in USoft Authoriser
- Added authorization options for components and SQL DDL operations.
- Automatic cache refresh
In USoft Authorizer, you no longer need a separate Application User record for the underlyingdatabase user. Correspondingly, on the Database tab of a USoft Binder 11 file, you can nowspecify what is the underlying RDBMS username/password combination and separately, in new “Front -end user” fields, the USoft authentication for which role -based access is granted viaAuthorizer.
Expressiveness
It is now possible to store initial data with the definition of the table in the Definer.## Export and import routines to and from XML and JSON are now able to handle binary data (BLOB data type), using the base64 encoding.The methods XML.Export and XML.MultiExportTables of the XML internal component now havea new parameter named 'LobAsCDATA' with possible values 'yes' and 'no'. The default is 'no'.
Removed and deprecated functionality in USoft 11.0
This section provides you with an overview of removed functionality and functionality which has become deprecated in 11.0 and which will be removed in a next minor/major version.
Removed functionality
The following deprecated functionality has been removed in version 11:
- The WebServiceClient java component, which was deprecated in version 10 . ForWebserviceClient calls, please use the new WebServiceClient dotNet component.
- RDMI:Automation Servers were deprecated in version 10. They have now been removed fromthe product. If you are on version 10 and still have components of type RDMI AutomationServers, you are advised to convert them to DotNet components before upgrading to 11.
- Oracle System Installation functionality has been removed. It could be used when runningagainst Oracle to perform space calculations, define table spaces and other system installationsettings. This functionality was outdated and deprecated in version 10.
- Table T_DISPLAY_DATATYPE has been removed from USoft Definer. It was not used anylonger.
Deprecated functionality
The following functionality has become deprecated in version 11:
- WebService Provider in USoft Definer. This functionality was already deprecated in version10.1, but the runtime settings for Web Service Providers in USoft Authorizer were not deprecated. Now this complete area has become deprecated. This includes:
- Web Service Providers in USoft Definer.
- Web Services in USoft Authorizer.
- UDDI functionality in USoft Authorizer (UDDI Registries, UDDI Businesses, etc.) To provid e services (REST, SOAP ...), please use USoft Service Definer 11 instead.
- The following data types have become deprecated:
- LONG
- LONGRAW
- NTEXT
- TEXT
- The
usergroup()SQL function is deprecated. Userole()instead. - The
RulesEngine.SetUsergroup()method is deprecated. UseRulesEngine.SetRole().